User interface and method of data navigation in the user interface of engineering analysis applications

ABSTRACT

A user interface and method. A user interface and method of using said interface that uniquely applies a web browser navigation style to engineering analysis applications is disclosed herein. The user interface, which may be implemented at least in part by use of a computer system, may comprise a browser panel, a tabbed workspace, a graphics view, a search box, and a search and select bar.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit under 35 U.S.C. §119(e) of the earlier filing date of U.S. Provisional Patent Application No. 61/654,661 filed on Jun. 1, 2012, the disclosure of which is incorporated by reference herein, and the earlier filing date of U.S. Provisional Patent Application No. 61/654,576 filed on Jun. 1, 2012, the disclosure of which is also incorporated by reference herein.

BACKGROUND

Representations of real-world physics and design take the form of networks of information: discrete, often reusable, concepts specifically related to other concepts. Imagine a graph, concepts arranged spatially, interconnected by labeled arrows. An engineer might draw a graph like this by intuition.

By numeric ID, text name, a folder analogy or graphical selection, users of engineering software have always networked information. The more sophisticated the data, the more scenarios considered, the more people involved, the more valuable this network becomes.

Analysis user interfaces have historically exposed data and functionality to suit available controls or to mirror underlying code. Conversations about physical engineering took on software engineering terms such as “tree”, “object”, “level”, “parent” and “child”.

This compromise made practical sense for products that performed relatively simple analyses of similar physics. A tree provided a fixed menu of data and functionality and implied a process. Users worked in terms of relatively simple objects inserted at locations in the tree like files inside folders on a hard drive. Relationships not implied by the tree structure were left to the user to define and interpret manually.

Over time, networks grew in size and complexity, and incorporated concepts that no longer fit into a particular tree structure. Patchworks resulted. Consistency and integration suffered. Workflows became convoluted. Projects filled with default and redundant data. Determining engineering intent required tedious manual investigation.

Fortunately, a paradigm exists for working with networks of information, one known to every user of any discipline at any level on any platform: the browser. Tabs, location, links, back/next, history, bookmarks, and search apply as well to an engineering project as to a website. A paradigm in which the user browses functionality and data can speak in real-world engineering terms and avoids the need to invent a universal tree structure (or multiple alternative tree structures). The browser paradigm accommodates diverse content by its nature, scales indefinitely, and is familiar across all modern platforms and smart devices. Windows 7 successfully uses a browser paradigm for searching and navigating data in libraries, disks and networks as well as Control Panel functionality in a seamless experience.

Many decades of CAE software development have seen significant paradigm changes, from static plots to interactive 3D, from plain text to visual menus to trees of objects. The leap from object hierarchies to engineering networks would be no less profound.

SUMMARY OF THE INVENTION

Disclosed herein is a novel user interface and method of using said interface that uniquely applies a web browser navigation style to engineering analysis applications. A website is a meaningful analogy for an analysis project because a well-designed web site facilitates fast data search and navigation, and exposes multiple data types in a consistent and predictable manner. The disclosed web browser style user interface and method accommodates diverse content by its nature, scales indefinitely, and is familiar across all modern platforms and smart devices. Tabs, location, links, back/next, history, bookmarks, and search apply equally well to an engineering project as to a website.

The disclosed user interface and method will offer a network of functionality and data unprecedented in its scope and diversity. Paradigms of the past will not scale to this ambition. This new approach is: engineering-focused, data-centric, modular, efficient, practical and contemporary.

The disclosed user interface and method may comprise in preferred embodiments: focus on the task at hand; filtered lists over complex, heterogeneous trees; relevant data and actions grouped and accessible in one display, not requiring hunting under tree levels and nested submenus; and search as a method of working with data and functionality.

The disclosed user interface and method allows navigation, for one preferred embodiment, from a boundary condition, to a table it references, to the library that stores the table, or to a specific parameter in a design table, or to all data located on the same topology, or to relevant items to create or actions to perform. The possibilities are limited only by engineering usefulness, not by the nature of the user interface controls.

Hyperlinks are used to allow the user to jump to related content, another location in the data model or a location in the help system, for example, with minimal manual navigation or searching and with an easy means of returning back to the previous content.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are described herein in by way of example in conjunction with the following figures, wherein like reference characters designate the same or similar elements.

FIG. 1 shows the main components of the user interface and their layout including, without limitation, a tabbed workspace, context bar or search and select bar, composite data view or browser panel, graphics view which may include in certain preferred embodiments a radial menu, and search box.

FIG. 2 shows one preferred embodiment of the composite data view of the user interface.

FIG. 3A shows one preferred embodiment of the context bar of the user interface of the user interface for solution monitors.

FIG. 3B shows one preferred embodiment of the context bar of the user interface of the user interface for a search for “mo.”

FIG. 3C shows one preferred embodiment of the context bar of the user interface of the user interface for selection of volume.

FIG. 4 shows one preferred embodiment of the search box of the user interface of the user interface.

FIG. 5 shows one preferred embodiment of the user interface in operation with an example of a pipe model.

FIG. 6 shows one preferred embodiment of the composite data view of the user interface for an example showing data for air.

FIG. 7 shows one preferred embodiment of the composite data view of the user interface for an example fluid flow analysis.

FIG. 8 shows another preferred embodiment of the composite data view of the user interface showing physics, material, phase models, boundary conditions, and solution data.

FIG. 9 shows one preferred embodiment of the composite data view toolbar of the user interface.

FIG. 10 shows one preferred embodiment of the context menu showing relationships, properties, selection and actions of the user interface.

FIG. 11 shows on preferred embodiment of the data selection in a composite data view of the user interface for an example inlet geometry properties and relationships.

FIG. 12 shows one preferred embodiment of the properties view of the user interface for an example inlet geometry.

FIG. 13 shows one preferred embodiment of the composite data view of the user interface for an inlet geometry.

FIG. 14 shows one preferred embodiment of the explorer in the user interface showing properties of phase models.

FIG. 15 shows one preferred embodiment of the property dialog for the user interface showing phase models properties.

FIG. 16 shows one preferred embodiment of the graphics view with a pop up menu for a specific example geometry.

FIG. 17 shows one preferred embodiment of the graphics view with a bar chart for a specific example geometry.

FIG. 18 shows one preferred embodiment of a home page for the user interface showing geometry options.

FIG. 19 shows one preferred embodiment of the contents of a study in schematic form on the user interface for a pipe model.

FIG. 20 shows one preferred embodiment of solution monitoring for the user interface for velocity residual and energy balance.

FIG. 21 shows one preferred embodiment of a radial menu with a gesture selecting the create option.

FIG. 22 shows one preferred embodiment of the creation context menu from the radial menu.

FIG. 23 shows one preferred embodiment of the radial menu navigation option.

FIG. 24 shows one preferred embodiment of an example of the radial menu for wall 1.

FIG. 25 shows one preferred embodiment of the context bar of the user interface.

FIG. 26 shows one preferred embodiment of the context trail of the user interface.

FIG. 27 shows one preferred embodiment of the available volumes from the context bar of the user interface.

FIG. 28 shows one preferred embodiment of the search box for the user interface.

FIG. 29 shows one preferred embodiment of an example of the search box for the user interface.

FIG. 30 shows one preferred embodiment of the start page showing the starting point for a new analysis using the user interface.

FIG. 31 shows one preferred embodiment of the available analysis for a pipe example using the user interface.

FIG. 32 shows one preferred embodiment of choosing to create a static analysis for a pipe example using the user interface.

FIG. 33 shows one preferred embodiment of choosing a fluid analysis for a pipe example using the user interface.

FIG. 34 shows one preferred embodiment of showing categories of inputs needed to complete a problem setup for a pipe example using the user interface.

FIG. 35 shows one preferred embodiment of the composite data view for an example fluid flow analysis with the physics option selected using the user interface.

FIG. 36 shows one preferred embodiment of the composite data view for an example fluid flow analysis showing a drop-down box using the user interface.

FIG. 37 shows one preferred embodiment of the composite data view for an example fluid flow analysis showing selection of more options using the user interface.

FIG. 38 shows one preferred embodiment of the composite data view for an example fluid flow analysis showing a property dialog with the model for k-epsilon selected using the user interface.

FIG. 39 shows one preferred embodiment of the composite data view for an example fluid flow analysis showing a property dialog with possible model selections including k-epsilon and Spalart-Allmaras models using the user interface.

FIG. 40 shows one preferred embodiment of the composite data view for an example fluid flow analysis showing a property dialog showing properties required for the Spalart-Allmaras model using the user interface.

FIG. 41A shows one preferred embodiment of the radial menu showing a graph of displacement as a central node using the user interface. FIG. 41B shows one preferred embodiment of the breadcrumb path between home and the displacement using the user interface. FIG. 41C shows one preferred embodiment of the breadcrumb path between home and the Analysis 1 using the user interface.

FIG. 42 shows one preferred embodiment of the radial menu showing a graph of section of Analysis 1 Parameter using the user interface.

FIG. 43 shows one preferred embodiment of the radial menu showing a graph of selection of a project parameter using the user interface.

FIG. 44 shows the computing system used in conjunction with the user interface.

FIG. 45 shows embodiments of the computing system used in conjunction with the user interface.

DETAILED DESCRIPTION

It is to be understood that at least some of the figures and descriptions of the invention have been simplified to illustrate elements that are relevant for a clear understanding of the invention, while eliminating, for purposes of clarity, other elements that those of ordinary skill in the art will appreciate may also comprise a portion of the invention. However, because such elements are well known in the art, and because they do not facilitate a better understanding of the invention, a description of such elements is not provided herein.

Aspects of the invention may be implemented by a computing device, system or processor and/or a computer program stored on a computer-readable medium. The computer-readable medium may comprise a disk, a device, and/or a propagated signal. The computing device may comprise, and/or be interconnected to, a mouse, a track ball, a keyboard, and/or a touch screen to receive input and/or commands. The computing device may comprise, and/or be interconnected to, a graphical display device that displays a graphic view of or for the engineering simulation software or project being utilized.

The computing system may include any suitable type of computing device (e.g., a server, a desktop, a laptop, etc.) that includes at least one processor and a graphic display device. The computing system may include one or more modules which are implemented in software. The software may include a module which implements the user interface as set forth and disclosed herein. This module may be interconnected with or act in concert with other software modules which implement engineering simulation applications.

FIG. 1 shows the main components of one preferred embodiment of the user interface and their layout. As shown in FIG. 1, in the disclosed user interface and method, a data selection is established via the composite data view or browser panel, the context bar or search and select bar, or the graphics view. The selected data's relationships are shown as sections and links in the composite data view or browser panel. The toolbar at the top of the view exposes context-sensitive actions. Actions, as well as data relationships, can also be accessed via links embedded within the view as set forth in FIG. 2.

The context bar or search and select bar shows a path to the current context in the project. The disclosed user interface is not strictly hierarchical, and multiple paths may point to the same context; for example “Analysis>Boundary Conditions>Force” and “Analysis>Variable Loads>Force” might be two contexts referring to the same location. A collection location path might look as depicted in FIG. 3A. While a search location path might look as depicted in FIG. 3B.

The path expands or contracts as the user selects items in the composite data view, graphics view, context bar or search box. The path is not a chronological recording of the user's selections. Rather, the path shows a logical trail from home to the current context in the user interface. A location path can be bookmarked for easy access at a later time. A selection in the context path will cause the composite data view and the graphics view to update in response to that selection.

Navigation via the context bar is possible in at least three ways. First, path entries can be clickable. For example, in the context trail in FIG. 3B, the user is currently displaying search results but can return to the Steady/Static Fluid Flow, Study or Unsaved Project displays by clicking on the link for each. Second, the Back and Forward arrows to the left of the bar move the active selection through the recent selection history. Third, the triangle/arrow path separators, when clicked, show drop-downs with related links that can be selected with the mouse. In FIG. 3C, the user has clicked on the > to the right of Model 1 in order to view the available volumes.

The user interface may include a search box. Searchable content includes named data entities, data and property types, standard or user-defined queries, topology, help documentation, report content and online content. The effect of a broad search capability is to flatten the user interface space, allowing the user to discover items whose location, existence or terminology isn't obvious and eliminating the need to browse through menus, trees or documentation looking for the desired content.

The visual outcome of a search will depend on the type of data that is found. As shown in FIG. 4, the user interface might provide: a dropdown of search options, suggestions and actions; a panel of organized results; or highlights in the graphics area.

FIG. 5 shows a preferred embodiment of the user interface in operation. A user interface with a large graphics area, and a text-based panel beside it, will be familiar to any user of computer-aided engineering software. The paradigm modernizes the layout by taking significant direction from the web browsing experience, as well as by factoring in lessons from touch interaction and alternative form factors. A website can be meaningful analogy for a simulation project because a well-designed web site facilitates fast data search and navigation, and exposes multiple data types in a consistent and predictable manner. The web browser paradigm accommodates diverse content by its nature, scales indefinitely, and is familiar across all modern platforms and smart devices. Tabs, location, links, back/next, history, bookmarks, and search apply equally well to an engineering project as to a website.

The disclosed user interface and the method of utilizing it may comprise in preferred embodiments: focus on the task at hand; filtered lists over complex, heterogeneous trees; relevant data and actions grouped and accessible in one display, not requiring hunting under tree levels and nested submenus; and search as a method of working with data and functionality.

The user interface and method encourages navigation, for example, from a boundary condition, to a table it references, to the library that stores the table, or to a specific parameter in a design table, or to all data located on the same topology, or to relevant items to create or actions to perform. The possibilities are limited only by engineering usefulness, not by the nature of the user interface controls.

The user may utilize a mouse to position the cursor over a selection and click to interact with the user interface controls. In an alternate preferred embodiment, mouse hover can be used to reduce mouse clicks and encourage exploration. In this alternate embodiment, the user does not need to click to interact with user interface controls as hovering the cursor over a selection is sufficient to cause pop-ups or drop-downs to appear.

Hyperlinks are used to allow the user to jump to related content—another location in the data model or a location in the help system, for example—with minimal manual navigation or searching and with an easy means of returning back to the previous content.

In a preferred embodiment, the user interface includes a tabbed workspace. A tab presents a view, often of specific data in a project. Tab design and behavior is deliberately analogous to web browser tabs. Tabs offer flexible and familiar view management and the ability to integrate diverse content with a consistent paradigm. A tabbed user interface allows a user to maintain and switch between multiple views of the active project. In one embodiment, there is only one copy of the data and potentially multiple views of it. In this one embodiment, one project may be open at a time.

The data and actions exposed within a tab are contextual to the current view within that tab. A context can be a specific data selection, a summary, a comparison, search results, a report, etc. A different tab will maintain a different context. For example, a user may keep the material library display open in one tab while working on problem setup in another. Also, in some preferred embodiments, the user will be able to tear tabs off the main window, like with browsers, and position them on multiple monitors for simultaneous visualization of different aspects of the project.

The file menu to the left of the first tab is present in certain preferred embodiments. It provides access to application-level actions like project loading and session exit. Actions executed from this menu will impact all open tabs.

A tab may be undocked from its host window, allowing the active project to be viewed in side-by-side windows. Each window may include the file menu, and any action taken via the File menu may affect all windows. Closing a tab does not close a project in some preferred embodiments. The last remaining open tab may not be closed in some preferred embodiments.

The user may open a new tab by clicking on the + symbol to the right of last open tab. The resulting tab will open to the home location in the context bar. The user may also open new tabs via composite data view links, keyboard shortcuts or context menu entries that navigate the user to requested data locations, similar to the “Open in New Tab” option that is common in web browsers. In one embodiment, when multiple tabs are open, a data change in one tab is immediately reflected in the other tabs.

In prior engineering simulation application user interfaces, such as for the ANSYS, Inc. Workbench 1 application, a tab represented an application. Each application retained its own look and feel. Multiple instances of an application tab were not allowed. The data presented in each tab was independent of data shown in other tabs.

In disclosed user interface and method, a tab is simply a user-requested view of the active project. The user may view the same project simultaneously in multiple tabs, where each tab can host a different viewpoint of the data. Conversely, the user is not required to use multiple tabs. All project data can be accessed and edited without ever leaving the default tab. Data-integrated applications are enabled to launch in their own separate windows. Data-integrated applications will not be hosted in tabs in one embodiment, although the applications such as the ANSYS, Inc. Workbench Project Schematic may be an integrated part of the disclosed user interface.

The composite data view or browse panel hosts the main data display, edit and navigation mechanisms. A typical use of this view is to show a mix of properties, relationships and actions that are relevant for a selected context. This view can be hidden to allow a full-window graphics display. When the selected context has detailed properties to define or edit, the composite data view shows the fields in an editor layout, with a user interface control appropriate to each field's data type as shown in FIG. 6.

If necessary the composite data view will resize its width to fit the context's properties. A large or complex set of properties that does not require 3D graphics can take over the whole window and use it to display tables, charts or any other data as appropriate to the context.

The composite data view supports immediate edit mode; that is, each property change is committed immediately to the data model. If the selected data must be edited in a “sandbox” mode, where several property changes are to be made and committed as a group to the data model, then a modal edit mode is available as described in the section titled property dialog.

In the composite data view, if a selected context has relationships in addition to or instead of detailed properties, then those relationships may be displayed in a summary view. The display is more than a simple list; key summary data can be shown for each item. The user can choose how the boundary conditions are listed—alphabetically, or grouped by type, for instance. In FIG. 7 for example, the user has asked to see all of the boundary conditions in the fluid flow analysis.

As another example, FIG. 8 shows a summary view of a different analysis. Any object in a summary view may be investigated in more detail by clicking on the object name, which is displayed as a link. A summary view uses coloring or other visual clues to indicate state. In FIG. 8, for example, the Boundary conditions link is highlighted in red to alert the user that attention is needed in this area of problem setup.

When showing a set of objects as in the examples above, the composite data view may include a convenient toolbar that allows for sorting, labeling and deletion of selected items, and creation of new items, one example of which is shown in FIG. 9.

One current embodiment of the user interface implementation shows data exclusively in a hierarchical tree format (though the data itself is not stored hierarchically). The entire tree is always visible, unless the user hides sub-branches by collapsing tree nodes.

In another embodiment, the user interface is not strictly hierarchical. Tree displays will be available, but the user interface will not be limited to fixed tree relationships as it was in the past. Context-sensitive lists, driven by system- or user-generated queries, will play a large role in the new paradigm.

In one current user interface implementation, a data selection is established by clicking in the tree. The selected data's relationships are hierarchical and are displayed as a tree hierarchy. The selected data's properties are shown in a separate property view under the tree display. Allowable actions are shown in a context menu as shown in FIG. 10.

In disclosed user interface and method, a data selection is established via the composite data view, the context bar or the graphics view. The selected data's relationships are shown as sections and links in the composite data view. The toolbar at the top of the view exposes context-sensitive actions. Actions, as well as data relationships, can also be accessed via links embedded within the view as shown in FIG. 11.

One embodiment of the user interface allows individual property editing in the properties view. The view's grid has inflexible column rules, often requires scrolling and lacks formatting for readability as shown in FIG. 12.

In one embodiment of the user interface and method, the composite data view provides sizing flexibility and rich layouts to efficiently use space and promote readability. FIG. 13, while not a complete representation of all of the inlet's properties, demonstrates the possibility of a more natural and appealing configuration.

The user interface may include a property dialog. One preferred embodiment of the composite data view supports only “immediate” property edit mode. When property changes must be collected and committed as a group, the property dialog will be available via an edit button instead. The property dialog is a modal dialog with OK/Cancel buttons. As with the composite data view, the property dialog allows for rich layout and flexible formatting. The property dialog cannot show the links and actions that the composite data view can show, but beyond that the two views share a common look and feel for individual property editing. Because a modal dialog introduces overhead in visual reorientation and window management, the use of the property dialog may or may not be desirable.

One embodiment of the explorer in the disclosed user interface and method is the user interface properties window as a floating dialog. Property edits within the explorer are collected and committed as a group when the close button is pressed. Because it is based on the properties view, the explorer shares the same inconveniences: inflexible column rules, a lack of readability, and the need to resize and scroll when viewing large property sets as shown in FIG. 14.

The property dialog improves usability over prior art such as fixed property grids due to the use of rich text controls in more natural layouts. Tabs separate logical groupings of properties as shown in FIG. 15.

The user interface may include a graphics view. In one preferred embodiment, the graphics view in the disclosed user interface and method provides an immersive environment for project setup and exploration through the availability of in-place, context sensitive controls and scene composition. In-place, context-sensitive controls that may allow the user to create and manipulate data without leaving the graphics window. For example, in the image in FIG. 16, the user is editing a constraint's properties via a pop-up in the graphics window rather than in a separate data view or explorer. Scene composition may include heads-ups displays of secondary data around the periphery of the graphics window to give the user relevant information without the need to click away from the graphics display. For example, the bar chart in the image in FIG. 17 augments the result contour display.

The user interface may include in-place controls. In-place controls may operate on selected data and may be invoked via the edit option in a radial menu, or via interactive annotations or tooltips. The in-place display shows the basic or common properties and actions for a data type. The user can access the full set of properties by clicking a link in the control. The full set is displayed in the composite data view or in the property dialog as appropriate for the data type.

The user interface may allow for scene composition. Heads-up control types include legends, tables and charts. These controls are interactive, allowing the user to edit data and change settings. The user can drag the heads-up controls to new locations within the graphics scene. The user can remove controls from and add controls to the graphics scene.

The user interface may allow for selection and highlighting. Selection is separate from highlighting in that highlighting is a temporary preview of a possible selection. Entities in the graphics view are highlighted in response to actions in other views, like relationship mouse-overs in the composite data view, and query result previewing in the search box. The graphics selection can be changed by clicking within the graphics view, or by making a selection in the composite data view or context bar.

The user interface may allow alternatives to the graphics view. While an interactive 3D graphics display is an option for the disclosed user interface and method, some data types do not require graphics. In those cases, a tab may present a page, a diagram, a worksheet or other content appropriate to the current context. FIG. 18 shows one embodiment of the home page, the options that are displayed to the user at startup and whenever the user selects home in the context bar. FIG. 19 shows the contents of a study in schematic form. FIG. 20 shows an example of solution monitoring. The composite data view can grow to fill up to the entire width of the window to accommodate more complex data editing—for example, to show the tables and graphs that are typically used for material editing.

The user interface may include a radial menu. A radial menu is a type of context menu in which the entries are arranged in a circular fashion. Though the radial menu concept has been around for decades, in recent years it has become more common in CAD and CAD applications. The graphics view in the disclosed user interface may use a radial menu in place of the linear context menu that is typical in existing engineering analysis applications. The radial menu, which can be gesture-based, will map naturally to touch interfaces when applications migrate there.

In one embodiment, the radial menu appears on a right-click in the graphics view. It can be operated in at least two modes. In one mode, the user may right-click, release, view the menu, then move the cursor to the desired menu entry and select that entry with a second click. As a streamlined alternative, the user may right-click and, holding the mouse button down, drag to an entry and then release to select that entry. To cancel a radial menu operation, the user returns the cursor to the center of the menu and (1) right-clicks again, or (2) releases the right button.

The radial menu may include a creation option. As shown in FIG. 21, in one embodiment of the radial menu, the create action is located along the left radius of the menu. The user holds down the right button and drags left. Moving past the target threshold fades in the create box. When the cursor enters the create box, the creation context menu appears as shown in FIG. 22. The system positions the box so the cursor arrives on top of the most likely option. Related items are above and below. The user can move the cursor further to the left to switch categories. It is possible to create an item with a simple mouse button click down, mouse drag left, and a mouse button release.

The radial menu may allow for navigation. FIG. 23 shows one embodiment of a radial menu configured for four entries, with the navigate action appearing on the right side. In this embodiment, the user has selected “Wall 1” in the graphics view (not shown). When the user right-clicks and moves the cursor to the right to select Navigate, a second radial menu appears as shown in FIG. 24. This menu allows the user to navigate to one of Wall 1's data relationships. The image on the right shows the user continuing the mouse movement in an upward direction to select Force 1.

When the user mouses over (but has not yet selected) radial menu options like navigation, fit and hide, the graphics view shows a preview of the effect of the action. The number and arrangement of entries on the radial menu is configurable by the user and may include any parameters or options currently known or used in engineering simulation software and applications or any options defined or needed by the user.

The disclosed user interface and method may also use a graphics view that uses a traditional linear context menu. The menu's entries may be dynamic and sensitive to the selected context, as are those in the proposed radial menu. While the same options can be displayed in either form of a context menu, the radial menu provides additional behaviors and visual clues that bring user efficiency and suggest a more modern look and feel.

The context bar or search and select bar shows a path to the current context in the project. To provide an example using the one implementation of the user interface and method, the “Main Inlet” selection in the tree shown in FIG. 25 might have a context of Project>Study>Steady/Static Analysis 1>Fluid Region 1>Boundary Conditions>Main Inlet.

Other options for the disclosed user interface and method are not strictly hierarchical, and multiple paths may point to the same context; for example “Analysis>Boundary Conditions>Force” and “Analysis>Variable Loads>Force” might be two contexts referring to the same location.

A location points to a context, and a context may be a single piece of data, as in the example above, or a collection, a comparison, a query, etc. A collection location might look as depicted in FIG. 3A. While a search location might look as depicted in FIG. 3B.

The bar is also a navigation tool, allowing the user to determine the current selected location project (at the analysis overview, viewing search results, or a particular boundary condition, for example) and also to move easily through the project and return to previously viewed locations.

The context trail expands or contracts as the user selects items in the composite data view, graphics view, context bar or search box. The trail in one embodiment is not a chronological recording of the user's selections. Rather, the trail shows the logical path from Home to the current context in the user interface. It is possible for a piece of data to be accessible from more than one path—for example, a manual navigation through the hierarchy may show a trail that is different from the trail shown for a search query that yielded the same data. A location can be bookmarked for easy access at a later time. A selection in the context trail will cause the composite data view and the graphics view to update in response to that selection.

In one embodiment of the current user interface and method, navigation via the context bar is possible in three ways. First, path entries are clickable. For example, in the context trail in FIG. 26, the user is currently displaying search results but can return to the Steady/Static Fluid Flow, Study or Unsaved Project displays by clicking on the link for each. Second, the Back and Forward arrows to the left of the bar move the active selection through the recent selection history. Third, the triangle/arrow path separators, when clicked, show drop-downs with related links that can be selected with the mouse. In the example in FIG. 27, the user has clicked on the > to the right of Model 1 in order to view the available volumes.

Other possible user interfaces show data exclusively in a hierarchical tree format (though the data itself is not stored hierarchically). The entire tree may always visible (though the user can collapse tree nodes) and the user navigates by clicking on the desired node.

Though not limited to hierarchical data display, the context bar in the disclosed user interface and method can show a path through a data hierarchy, as if the tree were laid on its side and filtered to just one branch. Clicking on a triangle in the path gives the user a choice of items related to the upstream item in the path. This behavior is analogous to clicking the + to the left of a tree node in order to view its children, though the context bar's display is not limited to data objects.

Using a search box in the user interface, the visual outcome of a search will depend on the type of data that is found. The user interface might provide: a dropdown of search options, suggestions and actions; a panel of organized results; highlights in the graphics area as shown in FIG. 28. As the user types in the search box, possible matches are previewed dynamically in the composite data view, the graphics window and in a drop-down box under the search text area, as applicable. FIG. 29 shows one example. Search results are presented as links. Clicking a link navigates within the tab to the content just as if web browsing. Content can vary greatly, from a table of data to a geometric location to a help topic.

The context bar updates dynamically as the user types each character for criteria in the search box, and the context path indicates the scope under which the search is executed as depicted in FIGS. 3B and 28. Search criteria can be complex. The user can search by text, by data type, by association or by attribute. A named search can be saved and executed again at a later point in time, much like a web query can be bookmarked and reused in a web browser. Other and current user interfaces may include a rudimentary search capability accessed via a menu entry or toolbar button.

The following steps demonstrate how a user would import a CAD part and choose to set up a fluid flow analysis. At startup, the user sees a start page. The user clicks on a thumbnail of a recently used geometry to use it as the starting point for a new analysis as shown in FIG. 30. After the geometry is loaded, the user views the available analysis types by hovering the mouse over the analysis button as shown in FIG. 31. The user chooses to create a static analysis as shown in FIG. 32. Multiple static analysis types are available. The user chooses a Fluid analysis as shown in FIG. 33. The project is populated with defaults for a fluid flow analysis, showing the user which categories of inputs are needed to complete the problem setup as shown in FIG. 34.

The following steps indicate one possible embodiment of the method a user might define the physics models for a fluid flow analysis using one embodiment of the disclosed user interface. From the analysis summary in the composite data view, the user clicks on the link for physics options as shown in FIG. 35. The composite data view displays the physics options summary. The user decides to change the turbulence definition and clicks on the drop-down box as shown in FIG. 36. Not seeing the desired turbulence model in the drop-down, which in one possible embodiment has learned the user's commonly used options and displayed them in the current view, the user clicks on the link for more options as shown in FIG. 37. A property dialog appears where the user switches the model from k-epsilon to Spalart-Allmaras as shown in FIGS. 38 and 39. The property dialog's contents may be changed dynamically to show just those properties required for the Spalart-Allmaras model. The user clicks OK to commit the change as shown in FIG. 40.

In the current and contemplated embodiments of the present user interface and method, the user may still be able see a tree view of the data. Although the tree may not be the primary navigation mechanism in some cases, it is still an appropriate view in some cases. A tree is often used to group similar data, as children of a common parent node. The disclosed user interface and method provides alternate means of finding and displaying these groups through the search box or through a summary display in the composite data view, for example.

Known text-based rules established in existing designs may be applied before the data arrives at the user interface layer, and their effect will be seen in the property displays in both the composite data view and the property dialog.

Consider the simple analysis of a beam, affixed on one end and displaced at the other. In the past, displacement was specified as an object in the tree contained inside an environment folder. Plain text details allude to relationships: Geometry=“1 Face”, Coordinate System=“Coordinate System”, “P” means driven by a parameter defined elsewhere.

Imagine displacement not as an object in a tree but as the central node on a graph as shown in FIG. 41A. A glance at the graph reveals the intent behind this particular displacement in a way not possible before. Its context is a specific analysis. It's based on a default displacement. It's labeled as a “Boundary Condition”, a “Support” and a “Beam Deflection”. Its topology is 1 geometric face. Its definition refers to a specific coordinate system. The current detail/parameter X is unique to the displacement (a non-default value). X is defined by a table. A reaction force calculation is defined in part by the displacement. Two other displacements are based on this displacement.

A familiar breadcrumb address identifies the full context of the displacement as shown in FIG. 41B. A simple left click on any blue link changes the address like browsing through a website. Clicking Analysis 1 navigates to the path shown in FIG. 41C.

The graph morphs to the graph shown in FIG. 42. This graph in FIG. 42 provides insight about the analysis. It's based on a default analysis. Two other analyses are based on it. The user labeled it “Beam Analysis.” Analysis type (the current detail/parameter) is default. It's the context for 10 items (listed by clicking the link). Its topology is a specific model. Clicking project navigates to the graph shown in FIG. 43. The project consists of three related and comparable analyses of the same geometric model. A choice of diagrams allows the user to focus on different aspects of the project at different levels of detail. Simple, flexible diagrams of this type might assume the role of today's project schematic.

In certain preferred embodiments, a user interface may display tabs across the top that work like tabs in web browsers. Below that, back/next buttons, an address that puts the current location into context, and a box that maybe used to search anytime, anywhere, for almost anything known to the application. The topmost portion of certain preferred embodiments of the user interface remains consistent no matter if the tabs contain 3D geometry, a 2D circuit diagram, a material definition, design charts and tables, or a report. The basic environment is familiar, predictable and integrated. Tabs allow any location to present itself in its natural form without the disorientation of out-of-context user interface controls cluttering the screen. A graph might fill a tab for exploring a complex project, or float in a corner like a legend, or, in many cases, not appear at all. Links or list items appearing elsewhere provide equivalent navigation. This is a user interface and method built for rapid navigation to related locations, with the option to open any location in a tab or window, and with the comfort of a Back button.

Other aspects of the user interface and method complete the typical work environment and may include visualization (for example, graphics, legend, chart, etc.), definition (for example, details/parameters and effective values), exploration (for example, data queries), and construction (for example, functionality queries). A definition might be simple or complex, depending on the location. The user might choose to view all effective details/parameters or only what's unique (non-default) to the location. Some aspects of a definition, such as dimensions or magnitudes, might appear dynamically on the topology. Exploration consists of a set of queries that provide a summary for the overall context of the location. For example, at a load one query might appear as 4 Materials

Steel. The analysis involving the load includes 4 materials; the loaded geometry is steel. Clicking Steel navigates to the application of the material, and from there the material definition. Clicking 4 Materials navigates to a materials summary, or clicking the right arrow lists all materials in a menu. Construction suggests functionality based on the location. Consider Add

Default

Boundary Condition

Support

. The software offers this because the current location is labeled as a “Support” and “Support” is labeled “Boundary Condition”. Clicking one of those links navigates to a list of labeled items valid to create in this context. Links to the left are more general. Clicking Default lists all categories of default items; clicking Add lists all ways of adding content (from defaults, from existing data, from external data, and so on). Right arrow menus allow the user to create an item with a single mouse gesture.

This paradigm favors: focus on the task at hand; specific lists over complex, heterogeneous trees; consistent browsing of data and functionality, versus hunting for functionality under tree levels and nested submenus; and search as a first-class method of working with data and functionality.

As implied by these descriptions, locations often do not directly correspond to a single underlying data object. A location might represent multiple objects (for comparison or composite editing), query or search results, lists of objects or functionality, a freeform geometry or mesh selection, a page, a worksheet, a diagram and so on. The paradigm encourages navigation from a boundary condition, to a table it references, to the library that stores the table, or to a specific parameter in a design table, or to all data located on the same topology, or to relevant items to create or actions to perform. The possibilities are limited only by engineering usefulness, not by the nature of the user interface controls.

Relationships connect locations in specific ways and form the basis for reuse, reengineering, flexible classification and user-directed organization. In the original examples “Displacement 2” was defined in terms of how it differed from “Displacement 1”. This avoids needless duplication, enables simplified views focused on differences, and allows editing with intent (e.g. apply in all cases versus change here only). The context of “Displacement 1” is “Analysis 1”, though it could be a library of reusable data or a context within the analysis the user introduced for meaningful organization. “Displacement 1” is classified with default and custom labels, like Gmail, which provides a criterion for many of the queries.

The result of all this is a dynamic engineering network that simplifies the user's experience by focusing on a current activity and working on the user's behalf to map out related information and possibilities in a flexible and familiar environment. The disclosed user interface and method addresses longstanding problems in terms of integration, scalability, extensibility, consistency, workflow and real estate. It leverages the potential of a flat and queryable underlying data model, and offers an obvious market differentiator for the coming decade.

The graph concept is consistent with the project schematic. It is simply another way of viewing data relationships. It's another way of viewing reuse. One example is a shared data folder in a tree being reused by multiple analyses. Another example is shared and reused data in a tree by icons.

A tree is one way of presenting data. A tree is good at showing hierarchy. A graph is another way of showing data relationships. A graph is more flexible than a hierarchical tree. Regardless of how data relationships are presented, what's important is that data is reused and easily combined to form meaningful and useful subsets of engineering simulations. When it comes to actually performing an engineering simulation, most of the work is done at the details of the data level. Trees and graphs are for higher level views of data relationships. A simple panel for data entry is sufficient for much of the work. Trees and graphs and even paths are useful for seeing and navigating the overall project.

Another embodiment of the user interface and method demonstrates some of these points in action. It is simply a page with a panel on the left that lists contents of a particular context. Whether the context is an analysis or a boundary condition make little difference. The panel morphs from one to the other very easily by simple clicks. The data relations are indicated by simple text, lists, and paths. A graph view is also contemplated and is very useful.

The user interface disclosed herein may be implemented in hardware, firmware, software and combinations thereof as part of a computing system 12. For embodiments utilizing software, the software may utilize any suitable computer language (e.g., C, C++, C#, Perl, Java, JavaScript, Visual Basic, VBScript, Delphi) and may be embodied permanently or temporarily in any type of machine, component, physical or virtual equipment, storage medium, or propagated signal capable of delivering instructions to a device. The user interface module 18 (e.g., software application, computer program) may be stored on a computer-readable medium (e.g., disk, device, and/or propagated signal) such that when a computer reads the medium, the functions and displays described herein-above are performed or generated. According to various embodiments, the above-described functionality of the user interface module 18 may be distributed amongst additional modules and/or sub-modules.

Although the user interface module 18 is shown as being integral with the computing system 12, it will be appreciated that according to other embodiments, the user interface module 18 is communicably connected to but separate from the computing system 12. For example, according to various embodiments, the user interface module 18 resides at a remote computing device which is communicably connected to the computing system 12.

As shown in FIG. 44, the computing system 12 may be communicably connected to a plurality of computing systems 20 via one or more networks 22. Each of the one or more networks 22 may include any type of delivery system including, but not limited to, a local area network (e.g., Ethernet), a wide area network (e.g. the Internet and/or World Wide Web), a telephone network (e.g., analog, digital, wired, wireless, fiber optic, PSTN, ISDN, GSM, GPRS, and/or xDSL), a packet-switched network, a radio network, a television network, a cable network, a satellite network, and/or any other wired or wireless communications network configured to carry data. A given network 22 may include elements, such as, for example, intermediate nodes, proxy servers, routers, switches, and adapters configured to direct and/or deliver data. In general, the computing system 12 may be structured and arranged to communicate with the computing systems 20 via the one or more networks 22 using various communication protocols (e.g., HTTP, HTTPS, TCP/IP, UDP, WAP, WiFi, Bluetooth) and/or to operate within or in concert with one or more other communications systems.

FIG. 45 illustrates various embodiments of the computing system 12. The computing system 12 may be embodied as one or more computing devices, and includes networking components such as Ethernet adapters, non-volatile secondary memory such as magnetic disks, input/output devices such as keyboards and visual displays, volatile main memory, and the processor 14. Each of these components may be communicably connected via a common system bus. The processor 14 includes processing units and on-chip storage devices such as memory caches.

According to various embodiments, the computing system 12 includes one or more modules which are implemented in software, and the software is stored in non-volatile memory devices while not in use. When the software is needed, the software is loaded into volatile main memory. After the software is loaded into volatile main memory, the processor 14 reads software instructions from volatile main memory and performs useful operations by executing sequences of the software instructions on data which is read into the processor 14 from volatile main memory. Upon completion of the useful operations, the processor 14 writes certain data results to volatile main memory.

Nothing in the above description is meant to limit the invention to any specific formulation, calculation, display, or methodology. Many display, formulation, calculation and methodology substitutions are contemplated within the scope of the invention and will be apparent to those skilled in the art. The embodiments described herein were presented by way of example only and should not be used to limit the scope of the invention.

Although the invention has been described in terms of particular embodiments in this application, one of ordinary skill in the art, in light of the teachings herein, can generate additional embodiments and modifications without departing from the spirit of, or exceeding the scope of, the described invention. Accordingly, it is understood that the drawings and the descriptions herein are proffered only to facilitate comprehension of the invention and should not be construed to limit the scope thereof. 

What is claimed is:
 1. An user interface, implemented at least in part by use of a computer system, for an engineering analysis application comprising: a browser panel; a tabbed workspace; a graphics view; a search box; and a search and select bar.
 2. The user interface of claim 1 wherein said browser panel includes a property dialog.
 3. The user interface of claim 1 wherein said graphics view includes a radial menu.
 4. The user interface of claim 1 wherein said browser panel comprises: a display of a plurality of properties that can be selected; a display of a plurality of relationships that can be selected; and a display of a plurality of actions that can be selected.
 5. The user interface of claim 1 that comprises a plurality of hyperlinks to allow a user to jump to selected content.
 6. The user interface of claim 1 that comprises a plurality of hyperlinks to allow a user to jump to another selected location.
 7. A user interface, implemented at least in part by use of a computer system, for engineering analysis applications comprising: a plurality of hyperlinks for navigation and access to actions within said engineering application; and a plurality of displays of location within the engineering analysis application.
 8. The user interface of claim 7 wherein said plurality of displays of location comprise: a search and select bar.
 9. The user interface of claim 7 additionally comprising a radial menu that allows selection of relationships, capabilities and navigation within the engineering analysis application through gestures.
 10. A computer implemented method for displaying a user interface for an engineering analysis application comprising: displaying a browser panel; displaying a tabbed workspace; displaying a graphics view; displaying a search box; and displaying a search and select bar.
 11. The method of claim 10 further comprising displaying a radial menu in response to input from a user; and selecting an item from said radial menu by a gesture from the user.
 12. The method of claim 10 further comprising navigating to a different location within the engineering analysis application utilizing a hyperlink.
 13. A computer implemented method for displaying parameters for use in engineering analysis software in a radial menu in a user interface, comprising configuring one or more processors to perform operations comprising: displaying a plurality of options in a radial orientation around a central node; receiving a gesture from a screen pointer selecting one of said options; displaying a second menu of parameters in response to receiving said gesture; and receiving a gesture from the screen pointer selecting one of said parameters displayed on said second menu.
 14. The method of claim 13 wherein said plurality of options comprises: a create option; a navigate option; a hide option; and a fit option.
 15. A user interface, implemented at least in part by use of a computer system, for an engineering analysis application comprising: at least one diagram showing the flow of data and operations within the engineering analysis application.
 16. The user interface of claim 15, wherein said diagram comprises at least one icon representing an operation.
 17. The user interface of claim 15, wherein said diagram comprises at least one icon representing a model.
 18. A user interface for computer implemented engineering analysis applications comprising: a web browser style display.
 19. The user interface of claim 18 wherein the web browser style display comprises: at least one tab; at least one location display; links that can be selected to access other data and locations within the application; back and next functions that can be selected to move to different displays; a history display; at least one bookmark display; and a search function display that can be selected to locate data and functionality within the application.
 20. The user interface of claim 18 wherein data and actions are grouped and accessible in one display in the web browser style display.
 21. The user interface of claim 18 wherein the web browser style display includes a search display that can be selected by a user to search for data and functionality.
 22. The user interface display of claim 18 wherein the web browser style display includes actions that can be selected by an user.
 23. The user interface display of claim 18 wherein the web browser style display comprises: links to data and actions that are grouped and accessible in one display; and a search display that can be selected by a user to search for data and functionality.
 24. A method of navigating within a computer implemented engineering analysis application comprising: selecting a hyperlink; displaying another location within the engineering analysis application in response to the selection of the hyperlink.
 25. The method of claim 24 wherein the location is in a computer program help system.
 26. The method of claim 24 wherein the location is on a data model within the engineering analysis application.
 27. The method of claim 24 wherein the location displays content associated with the hyperlink.
 28. The method of claim 24 further comprising: navigating from at one least boundary condition to a table it references; navigating to a library that stores the table; and navigating to at least one parameter in the table. 